Installing and commissioning the driver
This page takes you from an unlicensed driver to a working tile with a button that does something. It covers the setup wizard, the browser setup app, building your first control, and wiring it into Crestron Home programming.
- A licence key — a 30-day trial or a full key from the UI Dynamic product page.
An existing
CHUIDYNAMICkey works. - The address of whatever your first button will call, if you want to test an outbound request during
commissioning — for example a Shelly relay at
http://192.168.1.50/relay/0?turn=on.
1. Add the driver​
In the Crestron Home configurator, add a device to a room and search for UI Dynamic (listed in the catalogue as Dynamic User Interface V2, by manufacturer LCD). Adding it opens the setup wizard, which has two steps: Licence → Setup.
UI Dynamic on the entity model is a new driver. A site running the previous UI Dynamic driver must be commissioned again — the controls are rebuilt (or brought across with the converter), and any Crestron Home programming that referenced the old buttons must be rewired. The licence key carries over: the driver keeps the same product SKU.
2. Enter the licence key​
On the Licence step, paste the licence key and press Next. Use Buy a licence to open store.lcd.network if you need a key or a trial first.
This step gates the wizard: without a valid key the driver will not continue, and an unlicensed driver shows its tile but does nothing when a button is pressed. If the key is rejected, check it is correct and that the processor can reach the internet — the driver contacts the licence server to verify it.
The driver activates against the same identifier the previous CHUIDYNAMIC driver used, so re-licensing
a site that already had UI Dynamic re-uses its existing activation rather than consuming a second one.
3. Open the setup app​
The Setup step shows two links:
- SET UP TILES — the UI Dynamic setup app, where you build the controls.
- PRODUCT MICROAPP — the LCD product and licence page for this processor.
Open SET UP TILES. The app is served from the processor and opens in your browser. It has tabs for Buttons, Tile, Webhooks, Activity and Backup & migrate.
The same app is reachable any time from this wizard step — you do not have to re-run commissioning to change a tile later.
4. Build your first control​
On the Buttons tab, press Add. A control appears in the list, numbered 1. Give it:
- a Name — this names the control's Crestron Home programming events, so call it something you will recognise in a scene ("Gate", "Kitchen Fire");
- its states — one state makes a momentary button, two make a toggle, more make a cycle. For each state give a Label and an Icon. Icons are chosen from a searchable list of the built-in Crestron glyph names — see the note on icons.
Press Save to processor. Within a few seconds the tile appears in the room with your control on it.
Each control has an On reboot setting: Restore the last state (the default) or Force a fixed state. There is also a Re-announce the state after start-up toggle, which re-fires the control's current-state event on boot so downstream Crestron Home logic re-syncs with a state it cannot otherwise know.
A brand-new install seeds a few sample controls so there is something on the tile to look at. Delete them once you have built your own.
5. Set how the tile behaves (optional)​
The Tile tab controls the room tile itself:
- Press behaviour — Opens the buttons page (the default) shows your controls when the tile is tapped. Acts as a button (no page) turns the whole tile into a single control: a tap fires the button you choose under Presses, with no page behind it — and also raises a Tile pressed event for programming (see step 7). In the default Opens the buttons page mode, a tap opens the page and does not raise that event.
- State-change animation — Show a spinner while a control changes state gives the familiar "your press registered" cue: the control's icon spins briefly, for the Duration (ms) you set (250–10000, default 2000), then settles on the new state's icon. Turn it off for an instant swap.
6. Make the button do something​
To have a press fire an outbound request, open the control, expand a state (or On every press), and add a request — an HTTP call, or a UDP/TCP command. Press Send test request to fire it from the browser and confirm it works before you leave site. This is covered in full in Buttons that call out.
To have an outside system drive the control, use the Webhooks tab — see Webhooks in.
7. Wire it into Crestron Home programming​
Every control publishes named events and the driver exposes actions, so a tile control can both drive and be driven by automation.
- Events — in Crestron Home programming, this device's event list shows a named entry per control state and press, e.g. "Gate — Open", "Gate — pressed", plus a "Tile pressed" event when the tile is set to act as a button (step 5). Bind a scene or a notification to one.
- Actions — the driver exposes
SetElementState,SetElementDisplay,ToggleElement,PressElementandSetTileText, all taking the control's number. Use them to drive a control from a scene or a schedule.
The events are named after your controls and their states, so you bind to "Gate — Open" rather than a generic slot — and because they follow the control's identity, renaming a button keeps existing bindings working. The full detail is on Events and actions in programming.